Fix WinGet publish by setting release-tag explicitly#1924
Merged
adamtheturtle merged 1 commit intomainfrom Feb 7, 2026
Merged
Conversation
The winget-releaser action defaults release-tag to github.event.release.tag_name, which is empty for workflow_dispatch triggers. This caused the action to fall back to the branch name 'main', resulting in a 404 when looking up the release. Set release-tag to the actual version tag from the build job output.
adamtheturtle
temporarily deployed
to
development
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
winget-releaseraction defaultsrelease-tagtogithub.event.release.tag_name, which is empty forworkflow_dispatchtriggers. This caused the action to fall back to the branch namemain, then try to fetch a GitHub release with that tag, resulting in a 404.This adds
release-tag: ${{ needs.build.outputs.new_tag }}to bothwinget-releasersteps so the action looks up the correct release.Fixes the failure in https://github.com/VWS-Python/vws-cli/actions/runs/21775715153/job/62832005733
Note
Low Risk
Small CI/workflow change to make WinGet publishing deterministic, plus a minor dev-only dependency lock bump; minimal runtime impact.
Overview
Fixes the
workflow_dispatchrelease pipeline’s WinGet publish step by explicitly settingrelease-tag: ${{ needs.build.outputs.new_tag }}for bothwinget-releaserinvocations, ensuring the action looks up the correct GitHub release.Also bumps the locked dev dependency
pyreflyfrom0.51.0to0.51.1inuv.lock(including updated artifacts/metadata).Written by Cursor Bugbot for commit f945d00. This will update automatically on new commits. Configure here.